| 
 
  | 
 A crash refers to Lumion crashing to the Desktop (with or without errors). 
 Make sure to ask the customer to confirm that it’s a ‘proper’ crash and not the two other situations below.  | 
| 
 
  | 
 A crash does not refer to the PC becoming slow/unresponsive while rendering. This issue is discussed in the following article: 
 
  | 
| 
 
  | 
 A crash also does not mean that the PC restarts while rendering. This issue is discussed in the following Knowledge Base article: 
 
 
  | 
Diagnosis: Ask the customer to upload the model file and the original CAD file if applicable, so you can check if it also causes a crash on your PC. If it takes ages to import the file or if it makes Lumion crash, it almost always means that the model is too detailed for the available hardware.
Solution: Advise the customer to follow the instructions in the following article:
Diagnosis: Ask the customer about the grass and/or get them to upload the .LS Project file.
Solution: Advise the customer to follow the instructions in the following article:
Diagnosis: Ask the user to provide a Diagnostics Report and their Project file. Check if they are using 3D Grass and have one of those graphics cards.
Solution: Advise the customer to install the latest AMD graphics card driver. If the problem persists, the only other option is to follow the instructions in the following article:
Diagnosis: Ask the customer to follow the instructions in the following article:
Solution: If the HWInfo report shows that some readings exceed nominal temperature/clock frequency values for the CPU, graphics card and RAM just before the crash, tell the customer to check the cooling system or disable overclocking for the relevant components depending on the cause of the problem.
Diagnosis: Ask the customer to provide a Diagnostics Report:
Solution: Check if the graphics card meets the system requirements.
Diagnosis: Ask the customer to provide a Diagnostics Report:
Solution: Check if Windows is up to date and that the latest graphics card driver is installed:
Diagnosis: Ask the customer about the grass and/or get them to upload the .LS Scene file.
Solution: Advise the customer to follow the instructions in the following article:
Diagnosis: Ask the customer to follow the instructions in the following article:
Solution: If the HWInfo report shows that some readings exceed nominal temperature/clock frequency values for the CPU, graphics card and RAM just before the crash, tell the customer to check the cooling system or disable overclocking for the relevant components depending on the cause of the problem.
Diagnosis: Ask the customer to provide a Diagnostics Report and their Project file.
Solution: If you see in the report that the graphics card is not suitable for the level of complexity of their Project, advise them to follow the instructions in the following article:
Diagnosis: Ask the customer to let you know which of the factors in section 1 and 2 that apply to their situation:
Solution: If the customer confirms that one or more of the factors in the article apply, the instructions in section 2 in the article should prevent crashes from occurring again in the future.